Bump ModelContextProtocol and ModelContextProtocol.AspNetCore#959
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump ModelContextProtocol and ModelContextProtocol.AspNetCore#959dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
This was referenced Mar 30, 2026
intellitect-bot
approved these changes
Mar 30, 2026
d22b4d5 to
f4048bd
Compare
intellitect-bot
approved these changes
Apr 3, 2026
Member
|
@dependabot recreate |
f4048bd to
326fb08
Compare
intellitect-bot
approved these changes
Apr 17, 2026
326fb08 to
8024792
Compare
intellitect-bot
approved these changes
Apr 17, 2026
8024792 to
6635a94
Compare
intellitect-bot
approved these changes
Apr 21, 2026
6635a94 to
cfa6a0f
Compare
intellitect-bot
approved these changes
Apr 25, 2026
Bumps ModelContextProtocol from 0.3.0-preview.4 to 1.2.0 Bumps ModelContextProtocol.AspNetCore from 0.3.0-preview.4 to 1.2.0 --- updated-dependencies: - dependency-name: ModelContextProtocol dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: ModelContextProtocol.AspNetCore dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
cfa6a0f to
bd78c61
Compare
intellitect-bot
approved these changes
Apr 25, 2026
Member
|
@dependabot recreate |
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
auto-merge was automatically disabled
May 13, 2026 09:49
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated ModelContextProtocol from 1.2.0 to 1.3.0.
Release notes
Sourced from ModelContextProtocol's releases.
1.3.0
v1.3.0 focuses on improved transport diagnostics and security-focused documentation. The new public
ClientTransportClosedExceptiongives stdio and HTTP clients structured access to transport closure details (exit codes, process IDs, stderr tails, HTTP status codes) without parsing exception messages. Two reliability fixes harden the stdio process pipeline (preventing host crashes from userStandardErrorLinescallbacks) and correct the stateless HTTP transport's capability advertisement. New conceptual documentation covers role/identity propagation in tool execution, allowed-hosts and CORS guidance for HTTP servers, and aligns the docs information architecture with the MCP specification structure.What's Changed
ClientTransportClosedExceptionpublic and unify transport exception handling #1467 by @stephentoub (co-authored by @halter73 @Copilot)McpClient.CreateAsync(...)now surface asIOException(the newClientTransportClosedExceptionderives fromIOException) rather thanInvalidOperationException. Caller-triggeredOperationCanceledExceptionis also no longer wrapped, matching standard async cancellation semantics.Documentation Updates
Test Improvements
Repository Infrastructure Updates
... (truncated)
Commits viewable in compare view.
Updated ModelContextProtocol.AspNetCore from 1.2.0 to 1.3.0.
Release notes
Sourced from ModelContextProtocol.AspNetCore's releases.
1.3.0
v1.3.0 focuses on improved transport diagnostics and security-focused documentation. The new public
ClientTransportClosedExceptiongives stdio and HTTP clients structured access to transport closure details (exit codes, process IDs, stderr tails, HTTP status codes) without parsing exception messages. Two reliability fixes harden the stdio process pipeline (preventing host crashes from userStandardErrorLinescallbacks) and correct the stateless HTTP transport's capability advertisement. New conceptual documentation covers role/identity propagation in tool execution, allowed-hosts and CORS guidance for HTTP servers, and aligns the docs information architecture with the MCP specification structure.What's Changed
ClientTransportClosedExceptionpublic and unify transport exception handling #1467 by @stephentoub (co-authored by @halter73 @Copilot)McpClient.CreateAsync(...)now surface asIOException(the newClientTransportClosedExceptionderives fromIOException) rather thanInvalidOperationException. Caller-triggeredOperationCanceledExceptionis also no longer wrapped, matching standard async cancellation semantics.Documentation Updates
Test Improvements
Repository Infrastructure Updates
... (truncated)
Commits viewable in compare view.